fix: use modifyObjectKeys and snakeCaseObject on api data advanced settings to format values #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jignaciopm
requested review from
magajh,
dcoa,
luisfelipec95,
Asespinel,
bra-i-am and
DeimerM
jignaciopm
force-pushed
the
jipm/fix-setting-snake-case-redwood
branch
from
ef7b0ef to
e076ea2
Compare
…ttings to format values
jignaciopm
force-pushed
the
jipm/fix-setting-snake-case-redwood
branch
from
e076ea2 to
3f612c4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes this bug and this bug.
Community PR #1581
Testing instructions
camelCase(Review any field whose value is an object with configuration keys).BEFORE
AFTER
